System files must be monitored for unauthorized changes.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-224840	WN16-00-000240	SV-224840r804011_rule		Medium

Description
Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.

STIG	Date
Microsoft Windows Server 2016 Security Technical Implementation Guide	2022-03-01

Details

Check Text ( C-26531r804010_chk )
Determine whether the system is monitored for unauthorized changes to system files (e.g., .exe, .bat, .com, .cmd, and *.dll) against a baseline on a weekly basis. A properly configured and approved DoD ESS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. If system files are not monitored for unauthorized changes, this is a finding.

Check Text ( C-26531r804010_chk )

Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis.

A properly configured and approved DoD ESS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking.

If system files are not monitored for unauthorized changes, this is a finding.

Fix Text (F-26519r465423_fix)
Monitor the system for unauthorized changes to system files (e.g., .exe, .bat, .com, .cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools.